Online marketplace of plugins for enhancing dialog systems

ABSTRACT

A method for enhancing dialog systems is disclosed herein. The method comprises maintaining an online marketplace that may include a plurality of dialog system extension elements. Each of the plurality of dialog system extension elements may include at least one of a dialog system plugin, a dialog system add-on, a dialog system update, and a dialog system upgrade. The method may further include receiving a selection of one of the plurality of dialog system extension elements from a software developer. The software developer may be associated with a dialog system. The method may continue with associating the one of the plurality of dialog system extension elements with the dialog system of the software developer.

TECHNICAL FIELD

This disclosure relates generally to data processing and moreparticularly to dialog systems and an online platform allowingapplication developers to build, customize, and maintain dialog systemsfor software applications.

BACKGROUND

Currently, dialog systems are widely used in the information technologyindustry, especially in the form of mobile applications for cell phonesand tablet computers. A dialog system can include a computer-based agenthaving a human-centric interface for accessing, processing, managing,and delivering information. Dialog systems are also known as chatinformation systems, spoken dialog systems, conversational agents,chatter robots, chatterbots, chatbots, chat agents, digital personalassistants, automated online assistants, and so forth. All these termsare within the scope of the present disclosure and referred to as a“Dialog System” for simplicity.

Traditionally, a dialog system interacts with its users in naturallanguage to simulate an intelligent conversation and providepersonalized assistance to the users. For example, a user may generaterequests to the dialog system in the form of conversational questions,such as “What is the weather like in Palo Alto?” and receivecorresponding answers from the dialog system in the form of audio and/ordisplayable messages. The users may also provide voice commands to thedialog system requesting the performance of certain functions including,for example, generating e-mails, making phone calls, searchingparticular information, acquiring data, navigating, requestingnotifications or reminders, and so forth. These and otherfunctionalities make dialog systems very popular as they are of greathelp, especially for holders of portable electronic devices such assmart phones, cellular phones, tablet computers, gaming consoles, andthe like.

Although the demand for dialog systems for third party mobileapplications and web services is constantly growing, it is not an easytask to create a well-operating dialog system. Each dialog system has adialog system interface and dialog system engine. Dialog systeminterface is responsible for receiving user inputs and delivering dialogsystem responses to the user. A dialog system engine is responsible fortransforming voice user inputs into text inputs, interpreting textinputs, and generating corresponding responses to text inputs. Theprocess running on the dialog system engine is also known as “naturallanguage processing” or NLP. Development of NLP models is not only verytime consuming, but is also a highly technical task. Accordingly, mostapplication developers may struggle to develop a Dialog System forintegration with a particular mobile application or web service.Accordingly, there is a need in the art to simplify the process ofcreating, developing and maintaining dialog systems.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

Provided is a system for enhancing dialog systems. The system mayinclude at least one processor and a memory. The memory may be operableto maintain an online marketplace that may comprise a plurality ofdialog system extension elements. Each of the plurality of dialog systemextension elements may include at least one of a dialog system plugin, adialog system add-on, a dialog system update, and a dialog systemupgrade. The processor may be operable to receive a selection of one ofthe plurality of dialog system extension elements from a softwaredeveloper. The software developer may have a dialog system associatedwith the software developer. The processor may be further operable toassociate the one of the plurality of dialog system extension elementsselected by the software developer with a dialog system of the softwaredeveloper.

Provided is a method for enhancing dialog systems. The method mayinclude maintaining an online marketplace that may comprise a pluralityof dialog system extension elements. Each of the plurality of dialogsystem extension elements may include at least one of a dialog systemplugin, a dialog system add-on, a dialog system update, and a dialogsystem upgrade. The method may further include receiving a selection ofone of the plurality of dialog system extension elements from a softwaredeveloper. The software developer may be associated with a dialogsystem. The method may continue with associating the one of theplurality of dialog system extension elements selected by the softwaredeveloper with the dialog system of the software developer.

Additional objects, advantages, and novel features will be set forth inpart in the detailed description, which follows, and in part will becomeapparent to those skilled in the art upon examination of the followingdetailed description and the accompanying drawings or may be learned byproduction or operation of the example embodiments. The objects andadvantages of the concepts may be realized and attained by means of themethodologies, instrumentalities, and combinations particularly pointedout in the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are illustrated by way of example and not limitation in thefigures of the accompanying drawings, in which like references indicatesimilar elements and, in which:

FIG. 1 illustrates an environment within which systems and methods forenhancing dialog systems can be implemented, in accordance with someembodiments.

FIG. 2 is a process flow diagram showing a method for creating dialogsystem engines, in accordance with example embodiments.

FIG. 3 is a block diagram showing various modules of a dialog systemengine, in accordance with example embodiments.

FIG. 4 is a block diagram of a system for enhancing dialog systems, inaccordance with example embodiments.

FIG. 5 is a flow chart illustrating a method for enhancing dialogsystems, in accordance with example embodiments.

FIG. 6 is a high-level block diagram illustrating an example user devicesuitable for implementing the methods described herein.

DETAILED DESCRIPTION

The following detailed description includes references to theaccompanying drawings, which form a part of the detailed description.The drawings show illustrations in accordance with example embodiments.These example embodiments, which are also referred to herein as“examples,” are described in enough detail to enable those skilled inthe art to practice the present subject matter.

The embodiments can be combined, other embodiments can be utilized, orstructural, logical and operational changes can be made withoutdeparting from the scope of what is claimed. The following detaileddescription is, therefore, not to be taken in a limiting sense, and thescope is defined by the appended claims and their equivalents.

Present teachings may be implemented using a variety of technologies.For example, the methods described herein may be implemented in softwareexecuting on a computer system or in hardware utilizing either acombination of microprocessors or other specially designedapplication-specific integrated circuits, programmable logic devices, orvarious combinations thereof. In particular, the methods describedherein may be implemented by a series of computer-executableinstructions residing on a transitory or non-transitory storage mediumsuch as a disk drive or computer-readable medium. It should be notedthat methods disclosed herein can be implemented by a computer (e.g., adesktop computer, a tablet computer, a laptop computer), a game console,a handheld gaming device, a cellular phone, a smart phone, a smarttelevision system, and so forth.

The terms “application developer” and “software developer” or simply“developer” refer to one or more of the following: a software developer,a mobile application developer, a software engineer, a software owner, amobile application owner, a software manager, a mobile applicationmanager, a dialog system owner, and the like. Application developersdevelop and/or manage a Dialog System Engine and/or a Dialog SystemInterface.

The term “Dialog System” refers to one or more of the following: a chatinformation system, a spoken dialog system, a conversational agent, achatter robot, a chatterbot, a chatbot, a chat agent, a digital personalassistant, an automated online assistant, and the like. Each DialogSystem includes “Dialog System Interface” and “Dialog System Engine.”Each of these elements can be customized by an application developer.

The term “Dialog System Interface” refers to a computer-human interface,which is configured to acquire user inputs in the form of audio messagesor text messages, and deliver dialog system responses to the users inthe form of audio messages or displayable messages. In an exampleembodiment, a Dialog System Interface may be implemented as a widgetemployed to or integrated with a software application, a mobileapplication, a middleware application, a firmware application, awebsite, and web service, to provide a computer-human interface foracquiring user requests and delivering dialog system outputs to theusers.

The term “Dialog System Engine” refers to a software application, whichis configured to process user inputs and generate responses thereto. Inone example embodiment, a Dialog System Engine refers to acomputer-enabled or processor-enabled system for supporting anassociated Dialog System Interface by processing user requests andgenerating corresponding responses thereto.

The term “plugins” refers to one or more of the following: softwareplugins, add-ons, software extensions, updates, upgrades or softwarecodes for a Dialog System Engine. The term “plugins” is also referredherein to as “dialog system extension elements.”

The present technology provides for a platform enabling creation ofcustom Dialog System Engines serving as backend services for DialogSystem Interfaces. The platform may include an online platform (i.e., aplatform that resides on a server or network node). The presenttechnology also provides for an online marketplace, such as oneimplemented as a website or web service, for a plurality of dialogsystem extension elements including various plugins, add-ons,extensions, updates, or software codes for custom Dialog Systemapplications and custom Dialog Systems. The online marketplace can be apart of or connected to the platform to enable a software developer tocreate custom Dialog Systems and enhance the functionality of DialogSystems maintained by the platform. More particularly, by using theonline marketplace, software developers can extend functionalities ofdialog systems associated with the software developers by installingplugins available via the online marketplace and integrating theseplugins into the dialog systems.

Dialog System Interfaces can be implemented at least as a part ofvarious software applications, mobile applications, middlewareapplications, firmware applications, websites, web services, and soforth. In other words, Dialog System Interfaces may be on a client sideand may provide a computer-human interface configured to at leastacquire user inputs and deliver dialog system outputs to the users.Dialog System Engines, on the other hand, support the Dialog SystemInterfaces by processing user inputs and generating correspondingresponses thereto. Thus, the Dialog System Engine and the Dialog SystemInterface, when interacting with each other, form a Dialog System. Onemay refer to a Dialog System Interface running on or accessed from aclient device as a “frontend” user interface, while a Dialog SystemEngine, which supports the operation of such Dialog System Interface,can be referred to as a “backend” service.

In general, by selecting or purchasing a particular plugin at themarketplace, application developers may extend functionality of DialogSystems developed by or belonging to the application developers andultimately extend or alter functionality of software applications thatuse the Dialog Systems, as well as implement a particular function or abroad array of functions of the software applications that use theDialog Systems. Once a plugin is selected or purchased by a developer,the plugin can be automatically integrated with a particular DialogSystem Engine maintained by the platform. The plugin may have definedapplication programming interface signatures. Accordingly, when theDialog System Interface receives user requests, the user requests may beprocessed using plugins associated with the Dialog System Engine. Inother embodiments, user requests may be processed by internal modules ofthe Dialog System Engine, and if no “good” fulfillment can be found orno proper response can be generated, the user requests may be processedby the associated plugins. Therefore, this technology allows theapplication developers to enhance Dialog System functionalities withoutinvesting time in developing Dialog Systems having multiple DialogSystem rules.

The benefits of methods and system of the present disclosure can beevident from the following example. Assume a software developer needs tocreate a mobile application, such as a restaurant booking system, whichintegrates a Dialog System to allow users to make oral requests. Thesoftware developer may not have time or resources to create his ownDialog System, and thus the software developer may use an onlineplatform to create a custom Dialog System specifically for his or hermobile application. The mobile application may include only a DialogSystem Interface, which can accept user requests and deliver the userrequests to the custom Dialog System Engine for processing, as well asreceive responses from the custom Dialog System Engine and provide theresponses to the users through a displayable or audio message. Thecustom Dialog System Engine may reside at the online platform (i.e., ona server or network node). Normally, when the custom Dialog SystemEngine processes a user request, the Dialog System Engine may generate aresponse to the user request and cause the Dialog System Interface todeliver the response to the user. In order for the Dialog System Engineto operate normally, the software developer may need to create orcustomize rules (in some embodiments, this task may require creatingentities and intents which define dialog structures and fulfillmentexecution rules). However, this task can be time consuming in certaininstances. Moreover, even if the Dialog System Engine is properlytrained, there still can be functions that the Dialog System Engine maynot able to fulfill. In these cases, the software developer may improvefunctionality and operability of the Dialog System Engine by installingplugins. The software developer may simply need to open the onlinemarketplace and select one or more certain plugins the softwaredeveloper wants to add to the Dialog System. For example, there may be aplugin, which includes dialog system rules with certain entities andintents related specifically to online booking systems. Alternatively,there can be a plugin allowing the Dialog System to process userrequests in a foreign language. It shall be clear that there can be anumber of various plugins for fulfilling different needs. The softwaredeveloper can select or purchase plugins of interest at the marketplacein order to make the plugins of interest integrated with the particularDialog System Engine of the software developer. Once the plugin isinstalled, the plugin can handle user requests or parts of the userrequests so as to fulfill particular user needs. The plugins can becreated by third party developers and can be purchased or provided on afree-of-charge basis depending on a particular implementation.

Therefore, the present technology makes it very easy and fast forsoftware developers to create custom Dialog Systems for a wide range ofthird party mobile applications or web services, while adding plugins tothese Dialog Systems through the marketplace enhances Dialog Systemfunctionality. More specifically, the platform, according to variousembodiments of the present disclosure, allows for software developersand engineers to create custom Dialog System Engines that may supportfrontend Dialog System Interfaces. For example, if a software developerwants to integrate Dialog System functionality into a mobile applicationas an additional feature, the developer can use the platform to createand deploy a custom Dialog System Engine and link the custom DialogSystem Engine with the mobile application. The mobile application, inturn, may have only a Dialog System Interface. In this example, theDialog System Interface can be activated by a user when the userinteracts with the mobile application. The user can make inquiries tothe Dialog System Interface in the form of voice inputs or text inputs.Upon receipt of a user inquiry, the Dialog System Interface can transferthe user inquiry with little or no pre-processing to the linked customDialog System Engine, which was previously created using the platform.The Dialog System Engine may process the received user inquiry,interpret the user inquiry, and generate a response to the user inquirybased on predetermined rules and settings. The response may then bedelivered to the Dialog System Interface for further visual or audiopresentation to the user. In some embodiments, the response may includea response text to be delivered to the user and/or metadata withinstructions for the user device to perform an action (e.g., open abrowser, access certain data online, run a particular application,etc.). In other embodiments, the response may include a callback UniformResource Identifier (URI) that the Dialog System Interface or userdevice may need to access to obtain a response text and/or metadata orperform an action on the device/app represented by the URI.

In general, Dialog System Interfaces can be integrated or be an integralpart of a wide range of software applications running on a clientdevice, such as a personal computer (PC) or a cellular phone, or on aserver so that the Dialog Systems become a part of a website or webservice. Dialog Systems can be implemented on a server such that theirfunctionalities can be accessible to Dialog System Interfaces over theInternet, cellular networks, or any other communications means. Anonline marketplace can be also implemented in “a cloud,” meaning it canrun on a server and be available to software developers thorough aparticular website or web interface.

Referring now to the drawings, FIG. 1 shows a high-level block diagramof example system environment 100 suitable for practicing the presenttechnologies. As shown on FIG. 1, there is a platform 110 for creatingand maintaining custom Dialog Systems Engines. To these ends, theplatform 110 may include a platform interface 112 for creating customDialog System Engines and backend service 114 for maintaining andrunning custom Dialog System Engines 120.

The platform interface 112 may include a graphical user interface (GUI)embedded into a webpage and accessible by developers and/or engineers116 via the Internet. In some other embodiments, however, the platforminterface 112 may be implemented as a software application such as adownloadable software application or any other software, middleware, orfirmware running on or accessible from an electronic device such as acomputer. In the example shown in FIG. 1, the platform interface 112 maybe realized as a web accessible GUI as will be described below. Forsimplicity, this disclosure describes such embodiments where theplatform interface 112 is a server-based solution so that it isaccessible via the Internet. Regardless of a particular implementation,the platform interface 112 may enable the developers and/or engineers116 through a number of GUI tools to create one or more custom DialogSystem Engines 120.

Still referencing to FIG. 1, the backend service 114 of the platform 110may be responsible for maintaining and running the custom Dialog SystemEngines 120 that are created, for example, by or with the help of theplatform interface 112. The backend service 114 may operate as a webservice providing functionality to custom Dialog Systems by enablingDialog System Interfaces 130 to interact with the custom Dialog SystemEngines 120 maintained at the backend service 114 of the platform 110.

As briefly discussed above, the Dialog System Interfaces 130 can beprovided on a client side 140 associated with dialog system end users118. The Dialog System Interfaces 130 may be as simple as a GUI enablingthe dialog system end users 118 to make inquiries, which may be thendelivered to the backend service 114 for processing by the correspondingDialog System Engines 120, and to receive responses to the inquiresgenerated by Dialog System Engines 120. The Dialog System Interfaces 130may be implemented as a stand-alone software application or the DialogSystem Interfaces 130 can be an integral part of a software application,mobile application, web service, website, and the like.

Still referencing to FIG. 1, the client side 140 may refer to, but isnot limited to, a user device, a terminal, a computing device (e.g., alaptop computer, a tablet computer, a desktop computer, a PC), acellular phone, a smart phone, a gaming console, a remote control, amultimedia system, a smart television device, a set-top box, aninfotainment system, an in-vehicle computing device, an informationalkiosk, a robot, and so forth. In these embodiments, the Dialog SystemInterfaces 130 may be implemented as software, middleware, or firmwareinstalled on such devices.

In additional embodiments, the client side 140 may refer to a networkedor online solution, such as a server, hosting service, web service, website, cloud service, and so forth. For example, the Dialog SystemInterface 130 can be a widget or a GUI provided on one or more web pagesenabling end users to make inquiries and get responses to the inquiries.This option may be suitable for those instances when a developer, forexample, wants to integrate a Dialog System into a website of thedeveloper to provide enhanced customer service.

As can be seen in FIG. 1, the interaction between the Dialog SystemInterfaces 130 and the corresponding Dialog System Engines 120 may beperformed via a communications network 150. The communications network150 may include one or more of the Internet, intranet, cellular network,Local Area Network (LAN), Wide Area Network (WAN), IEEE 802.11 basednetwork, and so forth.

FIG. 1 also shows various third party web resources/web services 160provided via one or more web servers. These third party webresources/web services 160 can provide information of various types tothe Dialog System Engines 120 or the Dialog System Interfaces 130 as apart of a response to a user request. For example, the web resources/webservices 160 may refer to email services, weather services, navigationservices, and the like. Accordingly, if a user makes the inquiry “Whatis the weather like today?,” such information may be automaticallyacquired by the Dialog System Engine 120 from one or more third partyweb resources/web services 160 and then integrated into a dialog systemresponse to be delivered to the dialog system end users 118.

Still referring to FIG. 1, the example system environment 100 mayinclude an online plugin marketplace, shown as a marketplace 170, formaintaining a plurality of plugins. The marketplace 170 can beimplemented on a server such that it can communicate with the platform110. In some embodiments, however, the marketplace 170 can be integratedwith the platform 110.

The marketplace 170 may include a database 172 for storing plugins andrespective metadata. The marketplace 170 may also include a marketplaceinterface 174 for enabling the software developers to review, select,purchase, and/or optionally customize selectable plugins. Metadata mayaccompany each plugin and include content associated therewith. Forexample, metadata may include one or more of the following: adescription of plugins, example images, example audio messages, tags,developer comments, ranks, publisher information, payment information,statistical information (e.g., a number of downloads/installs), abusereport links/buttons, legal notices, hyperlinks to third party webresources, and so forth.

The marketplace interface 174 may include a GUI embedded into a webpageand accessible by the developers via the Internet. In some otherembodiments, however, the marketplace interface 174 may be implementedas a software application such as a downloadable software application orany other software, middleware, or firmware running on or accessiblefrom an electronic device such as a computer. In the example shown inFIG. 1, the marketplace interface 174 may be realized as a webaccessible GUI. For simplicity, this disclosure describes suchembodiments where the marketplace 170 is a server based solution so thatit is accessible via the Internet. Regardless of a particularimplementation, the marketplace interface 174 enables the developers,through a number of GUI tools, to select one or more plugins andassociate them with their custom Dialog System Engines 120.

As mentioned above, plugins can be provided to software developers whenpurchased or on a free-of-charge basis. In an example embodiment, theapplication developers may need to make a one-time payment or subscribeto a plan requiring regular payments. Accordingly, the marketplace 170may be enabled to make financial transactions using monetary ornon-monetary funds. For example, the marketplace 170 may have a creditcard processing agent, an Automated Clearing House agent, and the like.Subscription plans may require payments in amounts depending on a numberof dialog system users, period during which a plugin is used (e.g., aperiodic plan, such as a month-to-month subscription plan, a yearlyplan), number of plugin copies, complexity, number of functions providedby the plugin, and so forth.

Some plugins may be provided free of charge. In one example, plugins canbe provided free of charge during a predetermined period (e.g., a testperiod of one month), but then may require a payment. In another exampleembodiment, plugins can relate to free of charge open source agents.These free of charge open source agents can be collectively developed bya plurality of developers.

It should be noted that plugins can be provided by software developersor third party developers. For example, some plugins can be provided byan owner of the platform 110 and/or an owner of the marketplace 170. Inanother example embodiment, plugins can be provided to the marketplace170 by third party developers or companies. In yet another exampleembodiment, plugins can be provided to the marketplace 170 by softwaredevelopers. If plugins are sold from marketplace 170, the original ownerof the plugins may be compensated by the marketplace 170 from the fundscollected from purchasers. For instance, the owners of plugins sold canbe compensated as a percentage of the funds collected at the purchase.

According to some example embodiments, plugins can be shared amongsoftware developers. There may be several possible scenarios, including“knowledge sharing” and “black box sharing.” Under the “knowledgesharing” concept (also referred herein to as “white box” sharing),plugins may be shared by transferring definitions of entities andintents from one developer to another. This may be similar to sharingsource code among developers so that all of the developers cancontribute to a particular plugin. Under the “black box sharing”concept, developers on the consuming side may not have access to data,contents, entities, intents, and the like, and can use the plugin atruntime but not make any changes to the plugin.

In order for software developers, third-party developers, or companies(collectively referred to as “plugin developers”) to sell and/or shareplugins through the marketplace 170, they may be required to registerwith the marketplace 170 and establish a user profile. In someembodiments, marketplace personnel may review each plugin submitted by aplugin developer before publishing. The review may be required tomaintain high quality products and services for application developers.In yet more embodiments, plugin developers may be provided with aseparate interface (different from the marketplace interface 174), whichmay include statistical information associated with plugins of thesedevelopers, control modules, financial information, and so forth.

Accordingly, the marketplace 170 can be referred to a multi-user webplatform/web service allowing plugin developers to sell, distribute orshare plugins or elements of the plugins, and allowing applicationdevelopers to review, select, or purchase plugins of their interest, andintegrate them with custom Dialog System Engines.

The process of creating and operating custom Dialog System Engines 120will now be described with reference to FIGS. 1-3. In particular, theplatform interface 112 may provide one or more GUIs having a number oftools enabling developers to create and customize one or more dialogsystem elements, which serve as a basis for a custom Dialog SystemEngine 120.

According to various embodiments, dialog system elements includeentities and intents. Each entity may refer to a number of objectshaving the same or similar characteristics. In other words, entities mayinclude lists of terms and/or keywords defining objects of one class. Inone example embodiment, an entity may refer to a keyword and a set ofits synonyms. In another example embodiment, an entity may refer to akeyword and a set of its definitions. In yet another example embodiment,an entity may refer to a list (e.g., a list of cities, list of names,list of titles, list of brands, list of street names, etc.).

In some embodiments, each entity can have a title. For example, oneentity can be titled as “city” and may contain a list of cities such asAlexandria, Arlington, Boston, and so forth. In other embodiments, anentity can be titled as a keyword and can contain synonyms and/ordefinitions of this keyword. In one example embodiment, the entitycalled “music” may include the terms song, singer, singing, musician,and so forth. In another example embodiment, the entity called “artist”may include a list of music bands, music ensembles, or music artists. Inanother example embodiment, the entity called “Beatles” may include alist of possible synonyms, such as “The Beatles,” “Beatles,” “Fab Four,”“Liverpool Legends,” “John Lennon,” and so forth. In yet another exampleembodiment, there can be an entity called “Artist” which may includevarious artist names, artist name synonyms, music band names, and soforth.

In some embodiments, the Dialog System Engines may include a number ofdefault, pre-configured entities and/or intents. These can includecommon types of entities or intents related to such concepts as time,date, location, and the like. For example, when a developer creates anew Dialog System Engine, it may already have a few entities of commontype such as “@System.Date” entity. This entity may cover linguisticconstructs related to particular dates and may include the followingterms: “today,” “tomorrow,” “next week,” “January 1,” “January 1 of nextyear,” “next Monday,” “the following Monday,” and so forth.

Further, each intent of a Dialog System Rule may include a dialog systeminteraction scheme, which may provide a particular relation between atleast one user request and at least one dialog system linguisticresponse or fulfilment response. The dialog system interaction schemecan be represented by a rule based on a relationship between aparticular action and at least one entity. Actions generally relate toformalized software objects such as JSON (JavaScript Object Notation)objects causing at least one processor to generate linguistic orfulfilment responses associated with at least one entity. Accordingly,each intent can be represented as a logical relation between at leastone action and at least one entity object, for example, as follows:

-   -   a) [Action] @[Entity]    -   b) [Action] @[Entities]    -   c) [Actions] @[Entity]    -   d) [Actions] @[Entities]    -   e) Text @[Entity]    -   f) Text @[Entities]    -   g) Text @[Entity] Text    -   h) [Action] Text @[Entity]

The procedures a) through d) mean that a particular Action or severalActions shall be performed by client side 140 and/or Dialog SystemInterface 130 with respect to a predetermined Entity or severalEntities. For example, one intent may be represented as “Play @Artist,”where @Artist is a developer-defined entity containing a set of artists.In this example, the intent orders the Dialog System Engine 120 toactivate the playback of at least one Beatles song, depending on acontext.

The procedures e) through h) mean that particular information in theform of text is provided with respect to a particular Entity. Forexample, the user request “Create a meeting with John at 1 p.m.tomorrow, please” may be presented as the following markup: [Action]Text @[sys.date-time] Text. Here, @[sys.date-time] refers to an entityassociated with time and date, while the phrase “Create a meeting”refers to a predetermined action to be performed by a Dialog SystemInterface 130 or Dialog System Engine 120 with a certain mobileapplication, software application, or web service. The element “Text”refers to content and not entity nor intent.

As mentioned above, a dialog system rule may cause generation oflinguistic response and/or fulfilment response as an answer to a userrequest. One example of linguistic response may include particularizedcontent deliverable as an audio message or displayable message.Fulfilment responses may refer to particular processor-executableinstructions for one or more software applications, middleware,firmware, web services, and the like that cause implementation of aparticular action. Some examples of fulfilment responses may includescheduling an event in a calendar mobile application, writing andsending a text message or email, searching for content at a web searchservice, building a route in a navigational software application, and soforth. In certain embodiments, at least some linguistic responses and/orfulfilment responses can be configured by developers. In otherembodiments, at least some linguistic responses and/or fulfilmentresponses can be pre-configured and be available as default responses.

In certain additional embodiments, developers can provide not entitiesand intents, but just example requests to illustrate intents andentities. In these embodiments, the platform 110 may automaticallydetermine, using machine-learning techniques, what entities and intentsare implied in example user requests and create corresponding rules. Forexample, a developer may simply provide example requests, such as “PlayBeatles” and “I'd like to listen to Madonna,” and the platform 110 maymatch “Beatles” and “Madonna” to existing entities (system's or user's)and generate corresponding “[Action] @[Entity]” rules automatically.

Thus, developers can use the platform interface 112 to generate aplurality of dialog system rules specific to a particular application orindustry. These pluralities of entities and intents form dialog systemrules (also referred to as dialog system elements) and enable the customDialog System Engines to perform certain actions or generate certainoutputs in response to a wide range of end user inputs.

FIG. 2 is a process flow diagram showing a method 200 for creatingcustom Dialog System Engines using a platform, shown as the platform 110on FIG. 1, and for operating the platform according to an exampleembodiment. The method 200 may be performed by processing logic that maycomprise hardware (e.g., decision-making logic, dedicated logic,programmable logic, and microcode), software (such as software run on ageneral-purpose computer system or a dedicated machine), or acombination of both. In one example embodiment, the processing logicrefers to one or more components of the platform. Notably, the belowrecited steps of the method 200 may be implemented in an order differentthan described and shown in FIG. 2. Moreover, the method 200 may haveadditional steps not shown herein, but which can be evident for thoseskilled in the art from the present disclosure. The method 200 may alsohave fewer steps than outlined below and shown in FIG. 2.

At operation 205, an application developer may be enabled to registerwith the platform. To these ends, the software developer may need tointeract with a platform interface. The registration may includecreating a developer profile, which can be maintained by the platform.The software developer profile may link (i.e., associate) a customDialog System Engine of this software developer and one or more DialogSystem Interfaces deployed on a client side. The linking may includestipulating Application Programming Codes, rules for interaction,destination addresses, and so forth.

At operation 210, the platform may receive from the software developerone or more entities and store the received entities at a localdatabase. In some embodiments, the entities may be not received, butcreated by the developer using web tools of the platform interface.

At operation 215, the platform may receive from the software developerone or more intents and store the intents at the local database. In someembodiments, the intents may be not received, but created by thesoftware developer using tools of the platform interface. As describedabove, the intents may be associated with the entities, and intents andentities together may form dialog system elements (custom rules enablingthe Dialog System Engine to generate responses tailored for specificneeds).

At operation 220, the platform may associate one or more entities withone or more intents to create (i.e., form) the custom Dialog SystemEngine. The custom Dialog System Engine may be associated with one ormore Dialog System Interfaces of the software developer.

Operations 205-220 illustrate a set-up process for the custom DialogSystem Engine, while the following operations 225-245 illustrate theoperation of the custom Dialog System Engine. Once all dialog systemelements of custom the Dialog System Engine are created, the dialogsystem elements may be maintained as a backend service and enable any ofthe associated Dialog System Interfaces to provide the fullfunctionality of the Dialog System to users according to predeterminedsettings.

At operation 225, the platform may receive a user request from anunidentified Dialog System Interface. The user request can be a voiceinput or text input. In some embodiments, the Dialog System Interfacecan pre-process the user input, for example, by recognizing spoken wordsand transforming the voice input into text input. In other embodiments,however, no pre-processing is performed by Dialog System Interface.

At operation 230, the platform may process the user request and identifythe Dialog System Interface and the Dialog System Engine associated withthe identified Dialog System Interface. To these ends, the user requestcan be accompanied by an identifier when the user request is sent fromthe Dialog System Interface to the platform.

At operation 235, based on the result of the identification at operation230, the platform may activate the custom Dialog System Engineassociated with the identified Dialog System Interface. At the sameoperation, the platform may also retrieve or identify one or more dialogsystem elements (i.e., one or more entities and one or more intents)based on the result of the identification at operation.

At operation 240, the Dialog System Engine may process the user requestusing identified dialog system elements (i.e., one or more entities andone or more intents) as retrieved at operation 235.

At operation 245, the Dialog System Engine may generate a response andsend the response to the Dialog System Interface associated with thecustom Dialog System Engine 120. The Dialog System Interface may thendisplay and/or playback the response to the end user depending onpredetermined settings.

FIG. 3 shows a high-level architecture of an exemplary Dialog SystemEngine 300, according to an example embodiment. It should be noted thateach module of the Dialog System Engine 300 or associated architectureincludes hardware components, software components, or a combinationthereof. The Dialog System Engine 300 may be embedded or installed in auser device or server, or may be presented as a cloud computing moduleand/or a distributed computing module.

In the embodiment shown, the Dialog System Engine 300 may include anAutomatic Speech Recognizer (ASR) 310 configured to receive and processa speech-based user input 305 into a sequence of parameter vectors. TheASR 310 may further convert the sequence of parameter vectors into arecognized input (i.e., a textual input having one or more words,phrases, or sentences). The ASR 310 may include one or more speechrecognizers, such as a pattern-based speech recognizer, free-dictationrecognizer, address book based recognizer, dynamically createdrecognizer, and so forth.

Further, the Dialog System Engine 300 may include an NLP module 320 forunderstanding spoken language input. Specifically, the NLP module 320may disassemble and parse the recognized input to produce utterances,which are then analyzed utilizing, for example, morphological analysis,part-of-speech tagging, shallow parsing, and the like. The NLP module320 may then map recognized input or its parts to meaningrepresentations.

The Dialog System Engine 300 may further include a dialog manager 330,which may coordinate the activity of all components, control dialogflows, and communicate with external applications, devices, services, orresources. The dialog manager 330 may play many roles, which includediscourse analysis, knowledge database query, and system actionprediction based on the discourse context. In some embodiments, thedialog manager 330 may contact one or more task managers (not shown)that may have knowledge of specific task domains. In some embodiments,the dialog manager 330 may communicate with various computational orstorage resources 340, which may include, for example, a contentstorage, rules database, recommendation database, push notificationdatabase, electronic address book, email or text agents, dialog historydatabase, disparate knowledge databases, map database, points ofinterest database, geographical location determiner, clock, wirelessnetwork detector, search engines, social networking websites, bloggingwebsites, news feeds services, and many more. In some embodiments,computational or storage resources 340 may include one or more webresources/web services 160 as shown on FIG. 1 and discussed above.

Referring back to FIG. 3, the dialog manager 330 may employ multipledisparate approaches to generate an output 360 in response to recognizedinputs. Some approaches include using statistical analysis,machine-learning algorithms (e.g., neural networks), heuristic analysis,and so forth. The dialog manager 330 may be one of the centralcomponents of the Dialog System Engine. The major role of the dialogmanager 330 may be to select the correct system actions based onobserved evidences and inferred dialog states from the results of theNLP (e.g., dialog act, user goal, and discourse history). In addition,the dialog manager 330 may be able to handle errors when the user inputhas ASR and NLP errors caused by noises or unexpected inputs.

The Dialog System Engine 300 may further include an output renderer 350for transforming the output 360 of dialog manager 330 into a formsuitable for providing to the user. For example, the output renderer 350may employ a text-to-speech engine or may contact a pre-recorded audiodatabase to generate an audio message corresponding to the output 360 ofthe dialog manager 330. In certain embodiments, the output renderer 350may present or cause to present the output 360 of the dialog manager 330as a text message, an image, or a video message for further displayingon a display screen of the user device. In some example embodiments, theoutput renderer 350 can constitute at least a part of the Dialog SystemInterface shown as the Dialog System Interface 130 on FIG. 1.

Still referring to FIG. 3, the Dialog System Engine 300 may include oneor more dialog system rules maintained in at least one rule database365. The Dialog System Engine 300 may also include or be associated withone or more context databases 370, which may maintain a plurality ofcontext description elements, such as lists of terms, keywords, phrases,expressions, context variables, context parameters (e.g., geolocation,system rate, GUI, etc.) associated with one or more dialog system rules.In other words, the context databases 370 may include informationsupporting the process of determining conversational or environmentalcontext for particular user requests.

The Dialog System Engine 300 may also include or be associated with oneor more statistics and usage databases 380, which may be configured toaggregate statistical or usage information associated with the operationof the Dialog System Engine 300 and/or associated Dialog SystemInterface and/or associated mobile or software application. For example,statistics and usage database 380 may accumulate dialog system logs,which can be later used for optimization of dialog system rules, dialogsystem responding schemes, training machine-learning algorithms ifemployed by Dialog System Engine 300, and so forth.

FIG. 4 is a high-level block diagram illustrating an example system 400for enhancing dialog systems described herein. In particular, the system400 may be a server-based solution suitable for running a platform 110and/or a marketplace 170 shown on FIG. 1.

Note that all components of the system 400 shown on FIG. 4 may includelogic elements, hardware components, software (firmware) components,virtual components, or a combination thereof. The system 400 mayinclude, relate, or constitute an integral part of one or more of avariety of types of devices and systems such as a general-purposecomputer, server, web server, network service, cloud-computing service,and so forth. Further, all modules shown in FIG. 4 may be operativelycoupled using any suitable wired, wireless, radio, electrical, oroptical standards.

As shown in FIG. 4, the system 400 includes the following hardwarecomponents: at least one processor 402, a memory 404, optionally one ormore storage devices 406, and optionally network interface 408. Thesystem 400 may also optionally include the following software or virtualcomponents: an operating system 410, one or more software applications420, and an interface 430 (such as a platform interface 112 and/ormarketplace interface 174 shown on FIG. 1). The interface 430 mayprovide a human-centric interface for accessing and managing informationas discussed herein.

In some embodiments, the processor 402 may be configured to implementfunctionality and/or process instructions for execution within thesystem 400. For example, the processor 402 may process instructionsstored in the memory 404 and/or instructions stored on the storagedevices 406. Such instructions may include components of the operatingsystem 410, the software applications 420, and/or the interface 430.

The memory 404, according to one example embodiment, may be configuredto store information within system 400 during operation. The memory 404,in some example embodiments, may refer to a non-transitorycomputer-readable storage medium or a computer-readable storage device.In some example embodiments, the memory 404 may be a temporary memory,meaning that a primary purpose of the memory 404 may not be long-termstorage. The memory 404 may also refer to a volatile memory, meaningthat the memory 404 may not maintain stored contents when the memory 404is not receiving power. Examples of volatile memories include randomaccess memories (RAM), dynamic random access memories (DRAM), staticrandom access memories (SRAM), and other forms of volatile memoriesknown in the art. In some examples, the memory 404 may be used to storeprogram instructions for execution by the processor 402. The memory 404,in one example embodiment, may be used to temporarily store informationduring program execution.

One or more storage devices 406 can also include one or more transitoryor non-transitory computer-readable storage media and/orcomputer-readable storage devices. In some embodiments, the storagedevices 406 may be configured to store greater amounts of informationthan the memory 404. The storage devices 406 may further be configuredfor long-term storage of information. In some examples, the storagedevices 406 include non-volatile storage elements. Examples of suchnon-volatile storage elements include magnetic hard discs, opticaldiscs, solid-state discs, flash memories, forms of electricallyprogrammable memories (EPROM) or electrically erasable and programmablememories (EEPROM), and other forms of non-volatile memories known in theart. In one example, the storage devices 406 can include a databaseshown as a database 172 on FIG. 1 (i.e., the storage devices 406 canstore and maintain multiple dialog system extension elements, whichinclude plugins, add-ons, extensions, etc.). In other embodiments, thestorage devices 406 can store and maintain user profiles and customDialog System Engines.

Still referencing to FIG. 4, the system 400 may include a networkinterface 408. The network interface 408 can be utilized to communicatewith external devices, servers, and networked systems via one or morecommunications networks such as one or more wired, wireless, or opticalnetworks including, for example, the Internet, intranet, LAN, WAN,cellular phone networks (e.g. Global System for Mobile (GSM)communications network, packet switching communications network, circuitswitching communications network), Bluetooth radio, and an IEEE802.11-based radio frequency network, among others. The networkinterface 408 may be a network interface card, such as an Ethernet card,optical transceiver, radio frequency transceiver, or any other type ofdevice that can send and receive information. Other examples of suchnetwork interfaces may include Bluetooth®, 3G, 4G, and WiFi® radios inmobile computing devices as well as a Universal Serial Bus.

The operating system 410 may control one or more functionalities ofsystem 400 or components of the system 400. For example, the operatingsystem 410 may interact with the interface 430, and may furtherfacilitate one or more interactions between the software applications420 and processor 402, memory 404, storage devices 406, and/or networkinterface 408. The operating system 410 may interact with or beotherwise coupled to the interface 430 and components of the interface430. Notably, the system 400 and its components may also interact withone or more remote storage or computing resources including, forexample, web resources, web sites, social networking websites, bloggingwebsites, news feeds, email servers, web calendars, event databases,ticket aggregators, map databases, points of interest databases, and soforth. Software applications 420, in essence, may provide functionalityto the platform and/or the marketplace and enable their operation.Alternatively, the software applications 420 may be additions to theplatform and/or the marketplace.

FIG. 5 is a process flow diagram showing a method 500 for enhancingdialog systems, according to an example embodiment. The method 500 maybe performed by processing logic that may comprise hardware (e.g.,decision-making logic, dedicated logic, programmable logic, andmicrocode), software (such as software run on a general-purpose computersystem or a dedicated machine), or a combination of both. In one exampleembodiment, the processing logic refers to one or more components of themarketplace 170 and/or the platform 110 shown on FIG. 1. Notably, thebelow recited steps of the method 500 may be implemented in an orderdifferent than described and shown in FIG. 5. Moreover, the method 500may have additional steps not shown herein, but which can be evident forthose skilled in the art from the present disclosure. The method 500 mayalso have fewer steps than outlined below and shown in FIG. 5.

The method 500 may commence at operation 510 with maintaining an onlinemarketplace. The online marketplace may be maintained by the memory andmay include a plurality of dialog system extension elements (e.g., adialog system plugin, a dialog system add-on, a dialog system update,and a dialog system upgrade). A software developer may view and selectparticular dialog system extension elements through a marketplaceinterface. In an example embodiment, the software developer can reviewmetadata associated with dialog system extension elements, reviewcomments of other developers or users, ranks, ratings, reviews,publisher's information, description, manuals, images, videos, legalinformation, and so forth.

At operation 520, a processor may receive at least one selection of adialog system extension element from the software developer. In anexample embodiment, the software developer is associated with a dialogsystem; i.e., the software developer may have the dialog systemdeveloped or it my be owned by the software developer.

In some embodiments, the selection may require making a financialtransaction so that the dialog system extension element can beintegrated with a particular Dialog System Engine. In these cases, thesoftware developer may need to make a subscription to a plan or make alump sum payment for the right to use the selected dialog systemextension element. More specifically, upon receiving the selection ofthe dialog system extension element, the processor may receive aselection of a subscription plan for the dialog system extension elementfrom the software developer. Furthermore, the processor may receive apayment for the dialog system extension element. The payment may beprovided by the software developer in accordance with the subscriptionplan.

At operation 530, the processor may associate the dialog systemextension element selected by the software developer with the dialogsystem of the software developer. For this purpose, the processor mayneed to identify the software developer or the dialog system associatedwith the software developer. The identification can be accomplished byan authorization process (i.e., requesting the software developer tologin with the online marketplace). More specifically, the processor mayreceive an authorization request from the software developer.

In this regard, the processor may communicate with the platform based onthe authorization data and access the records or user profile associatedwith the software developer and the dialog system of the softwaredeveloper. The records may be stored in the memory. Based on therecords, the software developer and the dialog system of the softwaredeveloper may be identified. Once the software developer and/or thedialog system of the software developer are identified, the processormay authorize an access of the software developer to the onlinemarketplace. The processor may further proceed to linking the dialogsystem of the software developer with the dialog system extensionelement selected by the software developer. For the linking, the dialogsystem extension element may be integrated or embedded into the dialogsystem of the software developer, or, alternatively, certain links ormetadata associated with the dialog system extension element may beintegrated with the dialog system of the software developer. In eithercase, the dialog system extension element may operate in conjunctionwith the dialog system of the software developer.

In an example embodiment, the software developer can obtain dialogsystem extension elements as “black box” solutions, meaning the softwaredeveloper may be not able to see source code, entities, intents, orother information of the dialog system extension element. Alternatively,the software developer can obtain dialog system extension elements as“white box” solutions, meaning the software developer may be able to seesource codes, entities, intents, or other information of the dialogsystem extension element. In yet more embodiments, various options inbetween “black box” and “white box” solutions can be provided, meaningthere can be provided various access levels which can allow the softwaredeveloper to view and edit particular elements of the dialog systemextension elements (e.g., access to intent execution results, but notdialogs definitions, intents and entities themselves). Alternatively,the software developer can be provided with a full open-source access tothe dialog system extension element. In other words, the dialog systemextension elements may be provided as open-source dialog systemextension elements editable by the software developer, restricted accessdialog system extension elements partly editable by the softwaredeveloper, and closed access dialog system extension elementsnon-editable by the software developer.

Further, when the dialog system extension element is successfullyassociated with the dialog system, the operation of the dialog systemcan be as follows. At operation 540, the processor may receive a userrequest from a dialog system interface. The dialog system interface maybe installed on a user device or a third party server. The dialog systeminterface may be associated with the dialog system maintained at theonline platform. At operation 550, the processor may identify a dialogsystem engine associated with the dialog system interface and, thus,with the dialog system. At operation 560, the processor, or the dialogsystem engine, may identify the dialog system extension element ormultiple elements associated with the dialog system engine. Optionally,an arbitration step can be performed to select between elements orpresent the user with multiple results at once. The arbitration step canbe performed by an arbitration application. At operation 570, the userrequest may be processed by the dialog system extension element alone orin conjunction with the dialog system engine to generate a response tothe user request. Finally, at operation 580, the processor may cause thedelivery of the response to the user. The delivery of the response mayinclude delivering, to the dialog system interface or to a user device,text, video, audio, and/or metadata, such as a callback URL where theuser device can obtain data for delivering to the user.

In certain embodiments, at operation 570, the dialog system engine mayattempt to process the user request without any dialog system extensionelements. Such processing may include activating the dialog system basedon the user request, retrieving one or more entities and one or moreintents as discussed above, and processing the user request by applyingone or more entities and one or more intents in order to generate aproper response or fulfilment action. If the processing of the userrequest in such a way was successful, the processor may proceed tooperation 580 so as to deliver the response to the user or make aparticular action. Alternatively, if the processing of the user requestby applying the dialog system engine itself is unsuccessful, the userrequest is processed by the dialog system extension element (or multipledialog system extension elements) so as to generate a substituteresponse to the user request. Once the substitute response is generatedby one or more dialog system extension elements, the method 500 proceedsto operation 580 as discussed above.

FIG. 6 is a high-level block diagram illustrating an example user device600 suitable for implementing the methods described herein. It is worthmentioning that all components of the user device 600 may include logicelements, hardware components, software (firmware) components, virtualcomponents, or a combination thereof.

The user device 600 may include at least an integral part of one or moreof a variety of types of devices and systems such as a general-purposecomputer, desktop computer, server, computer network, network service,cloud-computing service, and so forth. Further, all modules shown inFIG. 6 may be operatively coupled using any suitable wired, wireless,radio, electrical, or optical standards. As already outlined above, theuser device 600 may refer to a smart phone, wireless telephone,computer, such as a tablet computer or desktop computer, infotainmentsystem, in-vehicle computing device, and the like.

As shown in FIG. 6, the user device 600 may include the followinghardware components: at least one processor 602, a memory 604, one ormore storage devices 606, one or more input modules 608, one or moreoutput modules 610, a network interface 612, and a geo locationdeterminer 614. The user device 600 may also include the followingsoftware or virtual components: an operating system 620, one or moresoftware (mobile) applications 630, and a dialog system interface 130,which can be a stand-alone software application or be integrated intoone or more software applications 630. The dialog system interface 130may provide a human-centric interface for accessing and managinginformation as discussed herein, communicating with a dialog systemengine, and communicating with web resources/web services. According tovarious embodiments, the dialog system interface 130 can be virtual.

The processor 602 may be configured to implement functionality and/orprocess instructions for execution within the user device 600. Forexample, the processor 602 may process instructions stored in the memory604 and/or instructions stored on the storage devices 606. Suchinstructions may include components of the operating system 620 and thesoftware applications 630. The user device 600 may also include one ormore additional components not shown in FIG. 6, such as a housing, powersupply, communication bus, and the like. These elements are omitted soas to not burden the description of present embodiments.

The memory 604, according to one example embodiment, may be configuredto store information within the user device 600 during operation. Thememory 604 may refer to a non-transitory computer-readable storagemedium or a computer-readable storage device. In some examples, thememory 604 may be a temporary memory, meaning that a primary purpose ofthe memory 604 may not be long-term storage. The memory 604 may alsorefer to a volatile memory, meaning that the memory 604 may not maintainstored contents when the memory 604 is not receiving power. Examples ofvolatile memories include RAM, DRAM, SRAM, and other forms of volatilememories known in the art. In some examples, the memory 604 may be usedto store program instructions for execution by the processor 602. Thememory 604, in one example embodiment, may be used by software (e.g.,the operating system 620) or the dialog system interface 130 executingon the user device 600 to temporarily store information during programexecution. The storage devices 606 can also include one or moretransitory or non-transitory computer-readable storage media and/orcomputer-readable storage devices. In some embodiments, the storagedevices 606 may be configured to store greater amounts of informationthan the memory 604. The storage devices 606 may further be configuredfor long-term storage of information. In some examples, the storagedevices 606 may include non-volatile storage elements. Examples of suchnon-volatile storage elements include magnetic hard discs, opticaldiscs, solid-state discs, flash memories, forms of EPROM or EEPROM, andother forms of non-volatile memories known in the art.

Still referencing to FIG. 6, the user device 600 may include one or moreinput modules 608. The input modules 608 may be configured to receiveuser inputs. Examples of the input modules 608 may include a microphone,keyboard, keypad, mouse, trackball, touchscreen, touchpad, or any otherdevice capable of detecting an input from a user or other source in theform of speech, audio, or tactile actions, and relaying the input to theuser device 600 or components thereof.

The output modules 610, in some example embodiments, may be configuredto provide output to users through visual or auditory channels. Theoutput modules 610 may include a video graphics adapter card, liquidcrystal display monitor, light emitting diode monitor, sound card,speaker, or any other device capable of generating output that may beintelligible to a user.

The user device 600, in some embodiments, may include the networkinterface 612. The network interface 612 can be utilized to communicatewith external devices, servers, and networked systems via one or morecommunications networks such as one or more wired, wireless, or opticalnetworks including, for example, the Internet, intranet, LAN, WAN,cellular phone networks (e.g., GSM communications network, packetswitching communications network, circuit switching communicationsnetwork), Bluetooth radio, and an IEEE 802.11-based radio frequencynetwork, among others. The network interface 612 may be a networkinterface card, such as an Ethernet card, optical transceiver, radiofrequency transceiver, or any other type of device that can send andreceive information. Other examples of such network interfaces mayinclude Bluetooth®, 3G, 4G, and WiFi® radios in mobile computing devicesas well as a Universal Serial Bus.

The user device 600 may further include the geo location determiner 614for determining a current geographical location of the user device. Thegeo location determiner 614 may utilize a number of different methodsfor determining geographical location including, for example, receivingand processing signals of Global Positioning Systems, GLONASS satellitenavigation systems, or the Galileo satellite navigation system;utilizing multilateration of radio signals between radio towers (basestations); or utilizing geolocation methods associated with InternetProtocol addresses, Media Access Control addresses, Radio-FrequencyIdentification, or other technologies.

The operating system 620 may control one or more functionalities of theuser device 600 or its components. For example, the operating system 620may interact with the dialog system interface 130 and may furtherfacilitate one or more interactions between the software applications630 and one or more of the processor 602, the memory 604, the storagedevices 606, the input modules 608, and the output modules 610. As shownin FIG. 6, the operating system 620 may interact with or be otherwisecoupled to the software applications 630, the dialog system interface130, and components thereof. In some embodiments, the dialog systeminterface 130 can be included into the operating system 620 and/or thesoftware applications 630. Notably, the user device 600 and itscomponents, such as the dialog system interface 130, may also interactwith one or more remote storage or computing resources including, forexample, web resources, websites, social networking websites, bloggingwebsites, news feeds, email servers, web calendars, event databases,ticket aggregators, map databases, points of interest databases, and soforth.

Thus, methods and systems for enhancing dialog systems have beendescribed. Although embodiments have been described with reference tospecific example embodiments, it will be evident that variousmodifications and changes can be made to these example embodimentswithout departing from the broader spirit and scope of the presentapplication. Accordingly, the specification and drawings are to beregarded in an illustrative rather than a restrictive sense.

What is claimed is:
 1. A method implemented by one or more processors,the method comprising: receiving a user input that is provided by a userat a dialog system interface, the dialog system interface beingimplemented as a firmware application of a client device and beingassociated with and managed by a developer; in response to receiving theuser input, identifying a dialog system engine that is associated withthe dialog system interface at which the user input is provided;attempting to fulfill the user input using a portion of the dialogsystem engine that is created by and managed by the developer; inresponse to the attempting to fulfill being unsuccessful: generating aresponse, for the user input, using one or more dialog extensionelements, of the dialog system, that are not created by the developerand that are not managed by the developer, wherein the response includesat least one of: text to be delivered to the user or metadata includinginstructions to perform one or more actions, and transmitting theresponse, to the dialog system interface, for visual or audiopresentation of the response via the dialog system interface.
 2. Themethod of claim 1, wherein the response includes the text to bedelivered to the user and includes the metadata including instructionsto perform one or more actions.
 3. The method of claim 1, wherein theresponse includes the text to be delivered to the user.
 4. The method ofclaim 1, wherein the response includes the metadata includinginstructions to perform one or more actions.
 5. The method of claim 4,wherein the one or more actions comprise running a particularapplication.
 6. The method of claim 4, wherein the one or more actionsare performed with a certain web service.
 7. The method of claim 1,wherein generating the response, for the user input, using the one ormore dialog extension elements, of the dialog system, that are notcreated by the developer and that are not managed by the developer,comprises: generating the response using multiple of the one or moredialog extension elements.